home *** CD-ROM | disk | FTP | other *** search
Text File | 1994-06-02 | 57.7 KB | 1,381 lines |
-
-
- Serial File Copy
-
-
-
-
- Version 3.5
-
- Feb 1994
-
-
-
-
- This software is provided as-is.
- There are no warranties, expressed or implied.
-
-
-
-
-
- Copyright (C) 1989,1990,1991,1992
- By MarshallSoft Computing, Inc.
- All rights are reserved.
-
-
-
-
- MarshallSoft Computing, Inc.
- Post Office Box 4543
- Huntsville, AL. 35815
- (205) 881-4630 5-9M CST M-F
-
-
- _______
- ____|__ | (R)
- --| | |-------------------
- | ____|__ | Association of
- | | |_| Shareware
- |__| o | Professionals
- -----| | |---------------------
- |___|___| MEMBER
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Users Manual page 1
-
-
- TABLE OF CONTENTS
-
-
-
- Chapter Page
-
- 1.0 Introduction............................. 3
- 1.1 User Support......................... 3
- 1.2 ASP Ombudsman........................ 3
- 2.0 Summary of SFC Features.................. 4
- 3.0 Distribution Files....................... 4
- 4.0 Null Modem Cables........................ 5
- 4.1 Purchasing a Null Modem Cable........ 5
- 4.2 Building a Null Modem Cable.......... 5
- 5.0 Serial COM Ports......................... 7
- 6.0 Running SFC.............................. 8
- 6.1 Startup Menu........................ 9
- 6.2 Startup Problems.................... 10
- 6.3 Status Window....................... 11
- 6.4 Command Menu........................ 12
- 6.5 Terminating SFC..................... 13
- 6.6 CRC Calculations.................... 13
- 7.0 Support Programs......................... 14
- 7.1 CLONE, GETSFC, and PUTSFC........... 14
- 7.2 LOOPBACK............................ 14
- 7.3 TERM................................ 14
- 7.4 MODEM............................... 14
- 7.5 PORTEXAM............................ 14
- 7.6 CHECKCRC............................ 15
- 7.7 GETFILE and PUTFILE................. 15
- 7.8 DRIVES.............................. 16
- 7.9 SETCOM3 and SETCOM4................. 16
- 7.10 FLAGS............................... 16
- 8.0 Performance.............................. 17
- 8.1 Test Results........................ 17
- 8.2 Other Tests......................... 17
- 9.0 Using SFC to back up HARD DISKS.......... 18
- 10.0 User Registration........................ 19
- 11.0 Revision History......................... 20
- 12.0 Other MarshallSoft Products.............. 22
- 12.1 Personal Comm Library for C........ 22
- 12.2 Personal Comm Library for Pascal... 22
- 13.0 License.................................. 23
- 14.0 Warranty................................. 23
-
-
-
-
-
-
-
-
-
-
-
-
-
- Users Manual page 2
- 1.0 Introduction
-
- The Serial File Copy program SFC is designed to allow the transfer
- of disk files ( including entire directories which may themselves
- contain directories ) between any two IBM PC compatible computers
- using standard RS232 serial ports. The SFC program is particularly
- useful in copying files between IBM PC compatibles with 5.25"
- disks and those with 3.5" disks such as the IBM PS/2 and the
- various IBM PC compatible laptops. The computers must both be IBM
- PC compatible ( this includes the TANDY 1000 ) with 256 KB or more
- of RAM. SFC is also an easy way to backup a hard disk onto the
- hard disk of another computer.
-
- Both computers ( between which you want to transfer files ) must
- have RS232 serial ports configured for use with a modem. COM1,
- COM2, COM3 or COM4 may be used. Baud rate of 1200, 2400, 4800,
- 9600, 19200, 38400, or 115200 may be selected.
-
- 1.1 User Support
-
- If you are having a problem using SFC, call us at 205-881-4630
- between 5 PM and 9 PM CST Monday through Saturday, or FAX us at
- the same telephone number at any time (24 hours). You can also
- call at other times and leave a message, and call back later for a
- reply. However, we can only answer questions with respect to using
- the PCL4C library.
-
- You may also call our User Support BBS (2400 to 9600 baud, no
- parity, 8 data bits, 1 stop bit) at 205-880-9748 and leave a
- message (address it to the SYSOP). We will usually have a reply
- ready for you within 24 hours.
-
- The BBS is available 24 hours per day except at 2 PM Sundays for
- maintenanace. All files are in standard ZIP format. The BBS will
- contain the latest shareware version of all MarshallSoft products
- as well as related files such as:
-
- BUGS.ZIP -- Bug report.
- NEWS.ZIP -- Latest news regarding our products.
-
- Of course, you can always write to us. You should receive a reply
- within a week or so.
-
- 1.2 ASP Ombudsman
-
- MarshallSoft Computing, Inc. is a member of the Association of
- Shareware Professionals (ASP). ASP wants to make sure that the
- shareware principle works for you. If you are unable to resolve a
- shareware-related problem with an ASP member by contacting the
- member directly, ASP may be able to help. The ASP Ombudsman can
- help you resolve a dispute or problem with an ASP member, but does
- not provide technical support for members' products. Please write
- to the ASP Ombudsman at 545 Grover Road, Muskegon, MI USA
- 49442-9427, Fax 616-788-2765, or send a CompuServe message via
- CompuServe Mail to ASP Ombudsman 70007,3536.
-
-
-
-
- Users Manual page 3
- 2.0 Summary of SFC Features
-
- o Supports COM1, COM2, COM3 and COM4.
- o Supports baud rates from 1200 to 115200.
- o Select groups of files with DOS wildcards ( eg: *.DOC )
- o Select entire directories ( recursively ).
- o Complete disk & transfer status on screen.
- o On line help provided for all SFC commands.
- o Option to send only files with a later timestamp.
- o Option to send only files with ARCHIVE attribute set.
- o Option to send files with READ ONLY attribute set.
- o Load DOS Shell from within SFC.
- o Full 16 bit CRC checksum is used.
- o Bad file packets are automatically retransmitted.
- o Change logged drive and path from within SFC.
- o Display directories from within SFC.
- o File date & time preserved after copying.
- o Supports batch file lists ( lists of files to send ).
- o Option to send or skip any file from selected group.
- o Can print files on remote computer.
- o Choice of B&W or color displays.
- o Can save choices in configuration file.
-
- 3.0 Distribution Files
-
- If a previous version of SFC is used to copy the distribution
- files be sure to rename the older version so that there is no
- attempt to run the older version with the newer version. The
- following files should be on the SFC distribution disk:
-
- SFC.EXE -- The executable Serial File Copy ( SFC ) program.
- SFC.DOC -- The SFC Users Manual.
- SFC.HLP -- File required for on-line help ( Type F1 for help ).
- SFC.QRC -- Quick reference card.
- SFC.CFG -- SFC configuration file.
- SFC.INV -- Invoice ready to print (shareware only).
- SFCSW.EXE - Displays shareware screen for SFC (shareware only).
-
- Registered users are also provided with the following support
- programs. None are necessary in order to run SFC, but are provided
- as a "Thank You" for registering. For a description of these
- programs see the section on "Support Programs".
-
- CLONE.COM -- 'Clones' SFC on the target computer.
- CLONE.DOC -- CLONE documentation file.
- GETSFC.COM -- Created by CLONE on the target computer.
- PUTSFC.COM -- Sends SFC to GETSFC on the target computer.
- LOOPBACK.COM -- Performs loopback testing on specified port.
- TERM.EXE -- Simple communications program.
- MODEM.EXE -- Controls and displays modem control status.
- PORTEXAM.EXE -- Displays all information about specified port.
- CHECKCRC.EXE -- Computes the CRC for any file.
- DRIVES.EXE -- Displays disk drive usage for range of drives.
- SETCOM3.COM -- Installs COM3 address ( 3E8 ) in BIOS table.
- SETCOM4.COM -- Installs COM4 address ( 2E8 ) in BIOS table.
- FLAGS.EXE -- Examine, sets, or clears file attributes.
- GETFILE.COM -- Copies files from PUTFILE using BIOS calls only.
- PUTFILE.COM -- Copies files to GETFILE using BIOS call only.
-
- Users Manual page 4
- 4.0 Null Modem Cables
-
- A 'null modem cable' is necessary to connect two computers
- together using the RS232 modem ports. They are widely available or
- can be home built for less than $10.
-
- 4.1 Purchasing a Null Modem Cable
-
- A null modem cable can be purchased ready for use or can be
- assembled by connecting a 'null modem adapter' to a normal RS232
- modem cable. Null modem adapters and cables can be purchased from
- several sources such as Radio Shack and most electronics parts
- houses. "Computer Shopper" regularly carries advertisements for
- null modem adapters and cables. Be advised that not all null modem
- adapters and cables connect all the lines that may be necessary.
- Although all should work for SFC some may not work for the MSDOS
- CTTY command which is used by the CLONE program.
-
- 4.2 Building a Null Modem Cable
-
- Building the null modem cable is easy. The only tricky part is
- being absolutely positive that you have identified the correct
- pins. Refer to the diagrams below as necessary. The pin numbering
- is shown for the front of each connector, where the pins ( male )
- or holes ( female ) are located. When viewed from the back side (
- where the wires are soldered ) the pins and holes run in the
- opposite direction. Soldering is recommended, although solderless
- connectors which use crimp pins can be used instead. You can also
- solder each wire to a crimp pin as its much easier than soldering
- the wire directly onto the connector.
-
-
- Male DB 25 Male DB 9
- ***************************************** *****************
- * 1 2 3 4 5 6 7 8 9 10 11 12 13 * * 1 2 3 4 5 *
- * 14 15 16 17 18 19 20 21 22 23 24 25 * * 6 7 8 9 *
- *************************************** ***************
-
-
- Female DB 25 Female DB 9
- ***************************************** *****************
- * 13 12 11 10 9 8 7 6 5 4 3 2 1 * * 5 4 3 2 1 *
- * 25 24 23 22 21 20 19 18 17 16 15 14 * * 9 8 7 6 *
- *************************************** ***************
-
- DB 25 DB 9 Pin Definition
- 7 5 Signal Ground ( SG )
- 2 3 Transmit Data ( TX )
- 3 2 Receive Data ( RX )
- 20 4 Data Terminal Ready ( DTR )
- 6 6 Data Set Ready ( DSR )
- 4 7 Request to Send ( RTS )
- 5 8 Clear to Send ( CTS )
- 8 1 Carrier Detect ( CD )
-
-
-
-
-
- Users Manual page 5
- SFC itself requires only signal ground (SG), transmit (TX), and
- receive (RX) lines in order to operate. The first step is to
- determine the type of connectors required. Examine the RS232
- connectors on your computers. You will need to purchase connectors
- that mate with the computers connectors. For example, lets say
- that you have a laptop with a male DB 9 connector and a desktop
- with a female DB 25 connector. Then you need a female DB 9 and a
- male DB 25 connector for your cable. IBM ATs and laptops require a
- female DB 9 to mate while most XT class machines require a female
- DB 25 to mate.
-
- The DB 25 and DB 9 connectors can be purchased at most electronics
- parts houses. Radio Shack also stocks both solder type and
- solderless DB connectors.
-
- Next you will need about 6 feet of ordinary 4-wire solid phone
- cable, although any 3-wire cable of 24 to 20 gauge can be
- substituted. If the CLONE program is to be used then 5 wires are
- required. Up to 50 feet of cable can be used. Shielded cable is
- even better but not necessary. Cable can be purchased by the foot
- at most stores that sell it.
-
- Once the connectors and cable have been purchased you are ready to
- assemble your null modem cable. First connect the signal ground (
- SG ) line straight between connectors. Then connect Transmit Data
- ( TX ) from one connector to Receive Data ( RX ) on the other. If
- you wish to use the SFC cloning program CLONE you must also
- connect Data Terminal Ready ( DTR ) from the end connected to the
- computer running CLONE to Data Set Ready ( DSR ) on the other end.
- Some computers ( like my TANDY 3000 ) also require you to connect
- Request To Send ( RTS ) from the end connected to the computer
- running CLONE to Clear To Send ( CTS ) on the other end.
-
- You then should have either 3 ( or 5 in order to use CLONE ) lines
- connected between connectors. Once completed, test the TX and RX
- connections by running the TERM ( or any terminal emulator )
- program on both sides. Whatever is typed on one side is displayed
- on the other. Finally, test the remaining connections by cloning
- SFC from one computer to the other.
-
- Refer to the Pin Definition Table above in order to identify the
- correct pins for your connector. When viewing the connector side
- of both the DB 9 and DB 25 with the wide part at the top, the pins
- are numbered left to right, top to bottom. Most connectors have
- the pin numbers on the connector itself but are often difficult to
- read because they are very small.
-
- If you have never soldered before, you should use either
- solderless connectors ( you crimp the wires on ) or find a friend
- who has some experience soldering. Remember that soldering
- doesn't have to be pretty in order to work. Practice a little
- first with some spare wire if you are out of practice. When you
- have completed construction of your null modem cable, verify that
- the correct pins have been connected. If you cannot get SFC to
- operate, then most likely you made a mistake in constructing your
- cable.
-
-
-
- Users Manual page 6
- 5.0 Serial COM Ports
-
-
- IBM PC compatible computers can have up to four or more serial
- ports. The BIOS table located at address 40:0000 has room for
- four communication port addresses -- COM1 to COM4. During boot up,
- the COM1 and COM2 addresses are placed in the BIOS table providing
- that the hardware is present. Unfortunately, the COM3 and COM4
- addresses are not placed in the table in DOS versions before 3.3.
- This oversight can be corrected by using DEBUG to assemble the
- following program SETCOM3 which should be added to the
- AUTOEXEC.BAT file. When executed, this program will place the
- standard COM3 port address 03E8 in the BIOS table. For COM4,
- change 03E8 to 02E8 and [0004] to [0006].
-
-
-
- PUSH DS
- MOV AX,0040
- MOV DS,AX
- MOV AX,03E8
- MOV [0004],AX
- POP DS
- MOV AX,4C00
- INT 21
-
-
- If you have never used DEBUG, refer to your MSDOS manual for
- detailed instructions. SETCOM3.COM and SETCOM4.COM are provided
- with the registered version of SFC.
-
- For example, if your computer is configured with COM1, COM2, and
- COM3 but not COM4, put SETCOM3.COM ( but not SETCOM4.COM ) into
- your AUTOEXEC.BAT file so that it is run when your computer boots
- up.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Users Manual page 7
- 6.0 Running SFC
-
- To begin, you will need SFC loaded onto both computers between
- which you want to copy files. If one computer has a 5.25" drive
- and the other has a 3.5" drive but you have SFC on only one disk ,
- then you have 2 options: (1) You can use a general purpose
- communications program such as PROCOMM, QMODEM, or TELIX to copy
- the SFC files from one machine to the other, or (2) registered
- users can use the SFC CLONE.COM program ( See Appendix A ).
-
- Connect your PC compatible computers together with a null modem
- cable between the RS232 ports ( the port used to talk to a modem
- ). Be sure that you are using a proper null modem cable rather
- than a standard cable.
-
- Normally, SFC can be started on both computers by typing 'SFC' on
- each. This is referred to as the AUTOSYNC startup. On some
- computers, AUTOSYNC will not work well. In this case, choose one
- computer to be the MASTER and the other the SLAVE. It makes no
- difference which is which. Start SFC on the MASTER by typing "SFC
- M" followed by the ENTER key. Start SFC on the SLAVE by typing
- "SFC S" followed by the ENTER key. If AUTOSYNC is specified on one
- side, it must also be specified on the other.
-
- When SFC starts up, it looks for the SFC configuration file
- SFC.CFG in the current directory. If it is not there, it looks
- for the SFC environment variable "SFC=". If the environment
- variable exists, SFC will use it to find the configuration file.
- For example, suppose that SFC.EXE, SFC.HLP, and SFC.CFG are in the
- C:\DOS directory. If you have previously typed
-
- SET SFC=C:\DOS
-
- then SFC will be able to find the SFC.CFG & SFC.HLP files. The
- best approach is to put the SET environment statement in your
- AUTOEXEC.BAT file. The use of the SFC environment variable is
- optional, but recommended.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Users Manual page 8
- 6.1 Startup Menu
-
- After startup, a menu will be displayed at the bottom of the
- screen with 8 options. Use up and down arrow keys to move the menu
- bar -- use ENTER to make selection. Note that on-line help is
- available by typing function key 1 ( F1 ).
-
- CONNECT: Attempts to connect to the other computer. The baud rate
- must be the same on both computers. If you mistakenly start SFC
- with the wrong baud rate or port, type "CTRL" and "BREAK"
- simultaneously to kill SFC so that you can start over.
-
- SET BAUD: Allows the user to select the baud rate. Choose 1200,
- 2400, 4800, 9600, 19200, 38400, 57600, or 115200 baud.
-
- SET COM PORT: Allows the user to select the communications port,
- COM1 to COM4. SFC uses the port addresses in the BIOS table. If
- you have hardware installed for COM3 or COM4 you may need to
- install the port addresses in this table. See section 5.0. Of
- course, hardware must exist for the port selected.
-
- SET LPT PORT: Allows the user to select the printer port, LPT1 to
- LPT3 for printing by the remote system.
-
- B&W or COLOR: The toggles between black and white and color mode.
- Use "Save Config." ( see below ). When SFC is restarted, the
- selected mode will be in effect.
-
- TOGGLE FLAGS: Allows the user to toggle each of the five runtime
- options ( ARC, ASK, CHK, DIR, and R/O ). The current setting is
- always displayed in the status area. For a definition of the
- runtime options, see section 6.3.
-
- SAVE CONFIG: After selected the baud rate, COM port, LPT port, and
- B&W or color, use this selection to save the configuration. The
- next time that SFC is run, it will be initialized as configured.
-
- QUIT: Quits and returns to MSDOS.
-
- Set the port and/or baud rate on both computers if the default (
- COM1 at 115200 is not acceptable. Then select the CONNECT option.
- SFC will now attempt connection to the other computer.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Users Manual page 9
- 6.2 Startup Problems
-
- If the message "Connection completed" is not displayed then the
- computers are not talking to each other. The problem may be one of
- the following:
-
- (1) You must start SFC on both computers! SFC should be started on
- both computers within one minute of each other.
-
- (2) The wrong port is selected. For example, if SFC is told to use
- COM1 but COM2 is actually connected to the cable.
-
- (3) You may have selected different baud rates. They must match !
- Recall that the default baud rate is 115200.
-
- (4) You do not have a null modem cable connecting the two. A
- normal cable ( without a null modem adapter ) will not work. Test
- the null modem cable by running TERM or any terminal emulation
- program. Whatever is typed on one side is displayed on the other.
- If this does not happen then you have a problem with your null
- modem cable.
-
- (5) One of the computers may be configured as DCE ( in order to
- talk to a serial printer ) instead of DTE ( in order to talk to a
- modem ). In this case, a normal cable ( instead of a null modem
- cable ) will work.
-
- (6) Your serial port is defective. This is unlikely. Registered
- users can run LOOPBACK to test the port.
-
- (7) Your COM ports are not defined sequentially. Your first port
- must be COM1, the second COM2, etc. This means that you shouldn't
- have COM2 defined but not COM1.
-
- (8) Your PC is not IBM hardware compatible! For example, the
- TANDY 2000 is not hardware compatible with respect to the serial
- ports.
-
- Occasionally, SFC will run correctly for a while and then lock up.
- This is almost always due to a marginal homemade null modem cable.
- If you use SFC on a regular basis, then you should either buy or
- make a SHIELDED cable. Remember that typing "CTRL" and "BREAK"
- simultaneously will kill SFC if you get hung up and the menus
- don't work.
-
- If SFC will not connect, then use the manual mode on COM1 at 9600
- baud: Type "SFC M" on one computer and "SFC S" on the other. If
- you still cannot get communication between computers, registered
- users can call the technical support telephone number (205)
- 881-4630 after 5:00 PM CST Monday through Friday or Saturday after
- 2:00 PM CST for assistance.
-
-
-
-
-
-
-
-
- Users Manual page 10
- 6.3 Status Window
-
- The "Status" window contains information having to do with the
- status of SFC. The definition of each field follows:
-
- PORT: The Communications port ( COM1 to COM4 ) is displayed.
-
- BAUD: The baud rate ( 1200 to 115200 ) is displayed.
-
- UNIT: # bytes per allocation unit is displayed. Space for disk
- files is always allocated as a multiple of this value.
-
- DISK: The currently logged disk drive is displayed.
-
- PATH: The current directory path is displayed.
-
- MODE: Runtime mode is displayed.
-
- "ready" -- Displayed when ready to accept keyboard input.
- "MENU" -- Displayed after having selected a menu command.
- "send" -- Displayed while sending files.
- "receive" -- Displayed while receiving files.
-
- FREE: Free disk space in bytes is displayed.
-
- Five runtime options ( ARC, ASK, CHK, DIR, R/O ) are also
- displayed as either "On" or "Off". All options can be toggled
- between "On" and "Off" by use of the "Toggle Flags" selection of
- the command menu ( See section 6.4 ). All flags are normally off.
-
- ASK: Asks the user for permission before sending each file.
- Typically selected when using wildcards in specifying a range of
- files for which you wish to exclude some files.
-
- DIR: Enables sending of files in subdirectories ( recursively ).
- For example, to send all "*.ASM" files on the C drive, select the
- C drive and the root path, turn on the DIR flag, and then send
- "*.ASM" with "Send File(s)".
-
- CHK: Send only files with a later date & time if file already
- exists. Normally off, toggle this on if you want to do a backup
- of more recently modified files. "...skipped(CHK)" is displayed if
- the file is not copied because of the CHK option.
-
- ARC: Send only files where the ARCHIVE attribute is set, then turn
- off the ARCHIVE attribute. An ARCHIVE attribute is maintained by
- MSDOS for each file on your disk. It is automatically set each
- time the file is written to and closed. Please refer to your MSDOS
- manual.
-
- R/O: Allows the sending of read only (R/O) files. Many users mark
- their executable programs as read only using the MSDOS ATTRIB
- program. Since one normally doesn't need to back up applications
- and systems programs, the R/O flag provides a convenient method
- for excluding read only files from copies.
-
- Note: All options need only be set on the sending computer.
-
-
- Users Manual page 11
- 6.4 Command Menu
-
- The Command Menu contains the choices the user has once SFC has
- connected. Use the up and down arrow keys to move the menu bar and
- ENTER to make your selection. Once one of the choices is
- selected, the user can return without SFC performing the selected
- function by typing the ESC key. Type the F1 function key for help.
-
- QUIT: Quits SFC and returns to MSDOS.
-
- SET CURRENT DRIVE: Changes the currently selected drive. The user
- can "log onto" any legal DOS drive ( A, B, etc. ). If you change
- diskettes then you must always select the SET DRIVE option before
- continuing.
-
- SET CURRENT PATH: Changes the currently selected path. When this
- option is selected, a "Enter Path:" prompt is displayed. The user
- then edits the current path which is displayed.
-
- All paths must start with a backslash ( full path name ). When the
- user is satisfied, typing ENTER will save the path. Then MSDOS
- will attempt to change the "current" path. If successful, the new
- path will be displayed in the "Status" window.
-
- DIRECTORY: Displays a directory of files requested. When this
- option is selected, a "Enter files" prompt is displayed. The user
- then types the file or files ( using the MSDOS wildcards * and ?
- ). Filenames can be edited similarly to paths.
-
- SEND FILE(S): Sends files to the other computer. No special action
- is required on the receiving side except that both sides must have
- previously selected CONNECT. The user will be prompted for the
- filename in the same way as when "Directory" was selected
- including the use of the MSDOS wildcards * and ?. If you specify
- that a directory is to be sent and the DIR option is set to "On",
- then all files in that directory ( including other directories )
- will be sent. In this way entire directory structures can be
- copied. The date and time for normal files ( but not directories )
- will be preserved.
-
- An indirect file can also be specified by prefixing the filename
- by the '@' character. An indirect file is a standard ASCII text
- file containing the list of files to be sent. The indirect file
- must have been previously prepared and contain one filename (
- wildcards accepted ) per line. Indirect files are typically used
- to specify a list of files that are transferred on a regular
- basis.
-
-
-
-
-
-
-
-
-
-
-
-
- Users Manual page 12
- REMOTE PRINT: Sends the specified file to the remote ( other )
- computer for printing. No wildcards are allowed. The printing
- can be canceled at any time by typing any key before the normal
- end of the print job.
-
- TOGGLE FLAGS: Allows the user to toggle each of the five runtime
- options ( ARC, ASK, CHK, DIR, and R/O ). The current setting is
- always displayed in the status area. For a definition of the
- runtime options, see section 6.3.
-
- DOS SHELL: Loads the DOS shell, allowing the user to execute DOS
- commands. The user must be very careful not to execute any command
- that changes the serial ports or modifies the screen environment.
- Please note that many application programs do change the screen
- environment. It is safer to stay with the standard DOS commands
- unless a particular executable has been previously tested. Use
- the MSDOS EXIT command to return to SFC.
-
- When entering text in response to any of the above commands, type
- ESC to return back to the main menu without selecting. The editor
- starts in "Overstrike" mode ( each typed character overlays the
- previous character ), but can be switched to "Insert" mode ( each
- typed character is inserted at the cursor, shifting all characters
- to the right over one space) by typing the INSERT key ( which
- toggles between Overstrike and Insert mode ). The DELETE key
- deletes the character underneath the cursor. The END key moves the
- cursor to the end of the string, while the HOME key moves the
- cursor to the start of the string.
-
- 6.5 Terminating SFC
-
- A series of files being transmitted can be terminated ( without
- aborting the system ) by typing ESC on the sending side during
- transmission. The user will be returned to the SFC menu after the
- completion of the current file transmission.
-
- The user may break out of SFC at any time and return to MSDOS by
- typing "CTRL" and "BREAK" simultaneously. This should only be
- used when the program hangs for some reason and SFC does not
- respond to the keyboard. Always try to use the menu selection QUIT
- to quit SFC and return to MSDOS rather than Control Break.
-
- 6.6 CRC Calculations
-
- A full 16 bit Cyclic Redundancy Check ( CRC ) using the CCITT (
- The Consultative Committee in International Telegraphy and
- Telephony ) polynomial is used by SFC. The CRC of each file is
- computed before transmission by the sender and sent along with the
- file being transmitted. The receiver then computes the CRC of the
- received file and compares it to the CRC sent. If the CRCs match,
- then the file is considered to be correct and a "OK" is displayed.
- CRC calculations are considered to be the best available method
- for verifing data integrity. They are much superior to checksums
- and detect 99.99 percent of data errors. If an error is detected,
- the offending packet ( part of the file ) will be re-transmitted
-
-
-
-
- Users Manual page 13
- 7.0 Support Programs
-
- The following support programs are not necessary in order to run
- SFC but are provided as a "Thank You" for registered users.
-
- 7.1 CLONE, PUTSFC, and PUTSFC.
-
- Don't have SFC on the target computer ? The CLONE program
- provides a way to 'clone' SFC onto another computer. The program
- PUTSFC is used to send a copy of SFC to GETSFC which is created by
- CLONE on the target computer. With CLONE you only need your null
- modem cable to connect to computers with a different disk format.
- Cloning is fully described in CLONE.DOC.
-
- 7.2 LOOPBACK
-
- If you suspect that your serial port may be defective, then use
- LOOPBACK to test the internal circuitry. The serial ports have a
- built in 'loop back' test capability which is used by the LOOPBACK
- program. For example, to test the COM1 port, type 'LOOPBACK 1'
-
- 7.3 TERM
-
- Need a simple communications program to test your null modem cable
- ? TERM is a terminal emulator program in which everything typed
- on one machine is displayed on the other, and vice versa. Connect
- your two computers together with a null modem cable and then run
- TERM on each side. Usage is "TERM port baud" where port = 1,2,3,4
- and baud = 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200.
- For example, type "TERM 1 1200" for COM1 at 1200 baud.
-
- 7.4 MODEM
-
- The MODEM program is used to turn the modem control lines DTR and
- RTS on and off, and to display DTR, DSR, RTS, and CTS. MODEM can
- help you test out your null modem cable. For example, to work with
- COM3, type 'MODEM 3'. A menu will be displayed providing all
- options.
-
- 7.5 PORTEXAM
-
- The PORTEXAM program will tell you all you ever wanted to know
- about the status of any serial port. It reports the serial port
- address, the interrupt vector, the location of the ISR code, the
- status of all modem control and modem status lines, and if the
- serial interrupt is enabled. Very useful as a cable testing
- program and for advanced users. For example, to examine COM1 type
- 'PORTEXAM 1'. PORTEXAM does not reset the port so that the
- "current" status of the port can be examined.
-
- 7.6 CHECKCRC
-
- The CHECKCRC program is used to compute the Cyclic Redundancy
- Check ( CRC ) of any file ( sort of a 16-bit file 'fingerprint' ).
- For example, to compute the CRC of all files ending with the
- extension .DOC type 'CHECKCRC *.DOC'. Use the CHECKCRC program to
- verify that two copies of the same file are indeed the same file.
-
-
- Users Manual page 14
- 7.7 GETFILE/PUTFILE
-
- Your computer not IBM compatible ? Then GETFILE and PUTFILE may be
- your answer. GETFILE and PUTFILE are BIOS driven file transfer
- programs. They make use of the computer's BIOS so that any MSDOS
- computer with a serial port configured for a modem will work, even
- though the computer is not IBM hardware compatible.
-
- To begin, you MUST have a null modem cable connecting the two
- machines. The signal ground must be present, transmit and receive
- must be reversed, DTR should be connected to both DSR and CTS on
- the other side. Thus, you will have a 5 wire cable as diagrammed
- below.
-
- SG o----------o SG
- TX o----------> RX
- RX <----------o TX
- DTR o----------> DSR+CTS
- DSR+CTS <----------o DTR
-
- This requirement is dictated by your BIOS software. Unfortunately,
- some commercial null modem cables are not fully wired because
- communication programs for IBM compatibles never use the BIOS !
-
- Start GETFILE on the receiving computer first. For example, to use
- COM3 type:
-
- GETFILE 3
-
- If you get any error, then try it again. Next start PUTFILE on
- the source computer. For example, to use COM1 type:
-
- PUTFILE 1
-
- PUTFILE should prompt you for a filename. Wildcards are OK. For
- example, to send all files ending in ".PAS", type "*.PAS" --
- without the quote marks. When no more files are to be sent, just
- type ENTER on the PUTFILE side to terminate both GETFILE and
- PUTFILE.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Users Manual page 15
- 7.8 DRIVES
-
- Need a quick and easy way to determine how much free disk space is
- available ? DRIVES is a utility program that will list the volume
- label, total space and used space in kilobytes or megabytes for a
- specified range of logical drives. This is particularly helpfull
- when your system has more than one logical hard drive.
-
- DRIVES C -- Displays disk usage for drive C.
- DRIVES C F -- Displays disk usage for drives C through F.
- DRIVES A Z -- Displays disk usage for all drives on system.
-
- 7.9 SETCOM3 and SETCOM4
-
- Got COM3 and/or COM4 serial port hardware but SFC and other serial
- programs don't know its there ? The BIOS table is not updated by
- MSDOS ( through version 3.3 ) as is the case for COM1 and COM2.
- SETCOM3 updates the BIOS table for COM3 if you have serial port
- hardware installed at the standard COM3 address 03E8. Similiarly,
- use SETCOM4 if you have serial port hardware installed at the
- standard COM4 address 02E8. Place SETCOM3 and/or SETCOM4 in your
- AUTOEXEC.BAT file so that the BIOS table can be updated
- automatically at bootup.
-
- 7.10 FLAGS
-
- Need an easy way to examine, set, and clear the ARCHIVE, READ
- ONLY, and HIDDEN attributes of your files? Later versions of
- MSDOS provide the ATTRIB utility, which does the same thing except
- for hidden files. But if you don't have ATTRIB or want to change
- the HIDDEN attribute, use FLAGS. For example, "FLAGS +H *.SAV"
- sets the hidden attribute of all files ending in "SAV", whereas
- "FLAGS -H *.SAV" clears the hidden attribute. Use R for READ
- ONLY, H for HIDDEN, and A for ARCHIVE attributes.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Users Manual page 16
- 8.0 Performance
-
- The following benchmark results were obtained using a Tandy 1000 (
- 4.77 MHZ), a Tandy 1400LT ( 4.77 & 9.16 MHZ ), a Tandy 3000 ( 10
- MHZ ) computer, and a Gateway 2000 Cache computer ( 25 MHZ 80386
- DX ). Note that the 'standard' IBM PC runs at 4.77 MHZ. Virtual
- disks ( ramdisks ) were used in order to measure performance as
- independent of disk speed as possible. The use of hard disks will
- result in a little slower times than shown while the use of floppy
- disks will result in much slower times. The use of faster
- computers will result in faster times than shown. Three files
- were used: file A is 10,000 bytes long, file B is 50,000 bytes and
- file C is 100,000 bytes long. All times are in seconds and are
- from start to finish including ramdisk access. A baud rate of
- 115200 is used for all tests. Your results should be very
- similiar.
-
- 8.1 Test Results
-
- ****************************************************************
- * Source * Destination * File A * File B * File C *
- ****************************************************************
- * Tandy 3000 * Tandy 1000 * 2.2 * 9.8 * 14.7 *
- ****************************************************************
- * Tandy 3000 * Tandy 1400LT * 1.6 * 6.7 * 12.7 *
- ****************************************************************
- * Tandy 1400LT * Tandy 3000 * 1.5 * 6.1 * 12.1 *
- ****************************************************************
- * Tandy 3000 * Gateway 2000 * 1.25 * 5.2 * 10.1 *
- ****************************************************************
-
- 8.2 Other Tests
-
- The author has personally tested SFC on a TANDY 1000, TANDY 3000,
- TANDY 1400LT, and a 25 MHZ Gateway-2000 386DX Cache Computer.
-
- Serial File Copy has been benchmarked against several other
- shareware programs. All that we have tried ( 3 ) are slower when
- using the same baud rate. One program took almost twice as long to
- transfer files. If anyone finds a faster file transfer utility
- than SFC please write or call!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Users Manual page 17
- 9.0 Using SFC to back up HARD DISKS
-
- SFC is an easy way to back up one hard disk onto another hard
- disk. Of course, there must be sufficient room on the receiving
- disk.
-
- Normally, you only need to back up your work files that have
- changed since your last backup. You should have the masters of any
- application programs backed up to disk separately.
-
- To begin, it is usually a good idea to mark your system and
- application files as "READ ONLY" (R/O) using the MSDOS ATTRIB
- command. Registered users can use the FLAGS utility for this
- purpose if ATTRIB is not available. Unless the SFC R/O flag is
- set, these files will always be skipped by SFC. By the way, making
- your files "read only" affords you some degree of computer virus
- protection.
-
- The CHK flag can be used which will only allow copying a file with
- a more recent time and date on the source computer than on the
- destination computer. If you use this method, be sure that the
- clocks on your two computers are reasonably close - within a few
- seconds if you will be backing up immediately after updating a
- file.
-
- Alternately, the SFC ARC flag can be set which will only allow
- copying a file that has not been written to since the last SFC
- copy. SFC does this by only copying files with the MSDOS file
- ARCHIVE attribute set, then clearing this attribute. However,
- please note that MSDOS commands like BACKUP also clear the ARCHIVE
- attribute. This means that if you use BACKUP or some commercial
- backup program to make backups, don't use the ARC flag with SFC
- unless you know what you are doing. To backup one disk onto
- another, follow these steps.
-
- 1) Start SFC on both machines.
-
- 2) Select the proper drive and path on the source machine. To back
- up the entire disk, select the root path.
-
- 3) Select the proper drive and path on the destination machine.
- All files will be copied to the directory specified on the
- destination machine.
-
- 4) Set the DIR flag to Y using the "Toggle Flags" menu item on the
- source machine. This enables copying of directories.
-
- 5) Select "Send File(s)" and type "*.*" on the source machine.
-
-
-
-
-
-
-
-
-
-
-
- Users Manual page 18
- 10.0 User Registration
-
- The shareware version of SFC is provided so that you may
- personally determine the usefulness of SFC for yourself. If you
- can use SFC please register your use with us. Registration
- entitles the user to install SFC on up to 2 computers. Site
- licenses are available for situations where SFC will be installed
- on more than 2 computers. Call for prices. To register SFC, send
- $30 plus $3 S&H ( $6 outside of USA, Canada, and Mexico ) to:
-
- MarshallSoft Computing, Inc.
- Post Office Box 4543
- Huntsville AL 35815
-
- We accept American Express (account number, expiration date,
- exact name on your card, and AmEx billing address required),
- checks in US dollars drawn on a US bank, purchase orders (POs)
- from recognized US schools and companies listed in Dun &
- Bradstreet, and COD (street address and phone number required)
- within the USA (plus a $3 COD charge). Print the file SFC.INV if
- an invoice is needed. The registered package is mailed first class
- US Mail (packet air mail overseas) and includes:
-
- o Latest version of SFC.
- o No shareware screens.
- o All 12+ support programs - See 'Support Programs' section.
- o Notices of new versions.
- o One year telephone support ( voice ).
- o Backbone bound printed Users Manual.
-
- The registered user will receive the latest version by return
- mail. A 360 KB 5.25" diskette will be provided unless a 720 KB
- 3.5" diskette is requested when ordering.
-
- For those not yet ready to register SFC, a "Users License" is
- available for $5. This entitles the purchaser to the use of the
- shareware version of SFC. The user will also receive notices of
- new versions of SFC and other MarshallSoft Computing products. The
- $5 can also be applied to any future registration.
-
- The latest shareware version is always available for $7.50 ( which
- includes a $5 Users License ). A 360 KB 5.25" diskette is
- provided unless a 720 KB 3.5 diskette is requested when ordering.
- Order both media for $8.50.
-
- You can also order SFC from The Public Software Library (PSL)
- with your MC, Visa, AmEx, or Discover card by calling 800-242-4PSL
- (from overseas: 713-524-6394) or by FAX at 713-524-6398 or by
- CompuServe at [71355,470]. THESE NUMBERS ARE FOR ORDERING ONLY.
- The product number for SFC is 10907.
-
- If you wish to update from an older version of SFC, send $15
- plus $3 S&H ($6 outside of North America). Updates must be
- ordered directly from MarshallSoft Computing.
-
-
-
-
-
- Users Manual page 19
- 11.0 Revision History
-
- Version 1.0 -- 10 April 1989
-
- Original release
-
- Version 1.1 -- 30 July 1989
-
- Added ASK and CHK options.
- Moved DIR option from separate menu item to options menu.
- Fixed bug in disk file size reporting.
- Changed units of FREE from kilobytes to bytes.
- Changed internal parameters for easier synchronization.
- Increased PATH length from 58 to a full 64 characters.
- SLAVE side must start SFC with "SFC /S".
- Could not generate backslash on Tandy 1000.
-
- Version 1.2 -- 16 October 1989 ( no shareware version )
-
- Added a new AUTOSYNC mode as well as manual startup mode.
- Added help file support.
- Greatly expanded documention file.
-
- Version 1.3 -- 1 November 1989 ( no shareware version )
-
- Fixed problem with port COM2.
- Support the port and baud rate specified on command line.
- Simplified operation of AUTOSYNC.
- Added indirect file ( '@' file ) support.
- Added support for COM3 and COM4.
-
- Version 2.0 -- 10 November 1989
-
- Internal change to allow 4.77 MHZ PCs to run at 115200.
- Allows transfer of read only files.
-
- Version 2.1 -- 16 February 1990
-
- Added DOS Shell menu option.
- Modified AUTOSYNC for increased reliability.
- Increased buffer size to 2000 bytes for 57600 & 115200 baud.
- Provide cloning program and other supporting programs.
- Added ability to do remote printing.
- 'NO RESPONSE' error does not abort system.
- Fixed error in sending files > 50KB ( affected version 2.0 only )
-
- Version 2.2 -- 15 May 1990 ( no shareware version )
-
- Changing drives clears file message string back to "*.*".
- Minor changes and bug fixes.
-
-
-
-
-
-
-
-
-
- Users Manual page 20
- Version 3.0 -- 11 Aug 1990
-
- Supports both B&W and color displays.
- Supports configuration file (SFC.CFG)
- Added ARCHIVE & R/O flags to options.
-
- Version 3.1 -- 11 March 1991
-
- Added SFC environment variable.
- Fixed potential problem with color mode when SFC.CFG is missing.
- Shareware version now runs at 115200 baud.
-
- Version 3.2 -- 24 Nov 1991
-
- Removed directory stack limit of 50 sub-directories.
- Sub-directory ordering is always preserved.
- Work around for DOS 5.0 bug (when asking for help) implemented.
-
- MarshallSoft incorporated on December 23, 1991.
-
- Version 3.3 -- 10 February 1992.
-
- Fixed bug in 3.2 which occurred when copying directories starting
- from a subdirectory ( not the root ).
-
- Version 3.4 -- 1 July 1992
-
- Fixed bug in reporting number of files transfered.
-
- Version 3.5 -- 1 Feb 1994
-
- Fixed bug occuring when run on some very fast 486 machines.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Users Manual page 21
- 12.0 Other MarshallSoft Computing Products
-
- A shareware disk containing all MarshallSoft programs ( described
- below ) is available for US $7.50 drawn on a US bank ($10 outside
- of the US, Canada, and Mexico). A 360 KB disk is provided unless a
- 720KB disk is specified.
-
- 12.1 Personal Communications Library for C ( PCL4C )
-
- The Personal Communications Library for the C Language ( PCL4C )
- is an asynchronous communications library designed for experienced
- software developers programming in C. Four compilers are
- supported: Microsoft Optimizing C, Microsoft Quick C, Borland
- Turbo C, and MIX Power C. An IBM PC/XT/AT or compatible is
- required.
-
- The PCL features SMALL, COMPACT, MEDIUM & LARGE memory models, 32
- communication and support functions, support for 16550 UART,
- hardware (RTS/CTS) flow control, interrupt driven receiver,
- support for 300 through 115200 baud, support for COM1 through
- COM4, adjustable receive queues from 8 bytes to 32 KB,
- control-BREAK error exit, 17 communication error conditions
- trapped, ability to run 2 ports concurrently, complete modem
- control & status, and a terminal emulator program ( source )
- featuring file transfer using XMODEM, YMODEM, and YMODEM-G.
-
- Registration for PCL4C is $65 plus $3 S&H ($6 outside of the USA,
- Canada, and Mexico), and includes printed documentation, libraries
- without the shareware screen, and SOURCE code for the library.
-
- 12.2 Personal Communications Library for Pascal ( PCL4P )
-
- The Personal Communications Library for Pascal ( PCL4P ) is an
- asynchronous communications library designed for experienced
- software developers programming in Turbo Pascal ( version 4.0 and
- up). An IBM PC/XT/AT or compatible is required.
-
- The PCL4P features 28 communications and support functions,
- support for 16550 UART, hardware (RTS/CTS) flow control, interrupt
- driven receiver, support for 300 baud to 115200 baud, support for
- COM1 through COM4, adjustable receive queues from 8 bytes to 32
- KB, control-BREAK error exit, 17 comm error conditions trapped,
- ability to run 2 ports concurrently, complete modem control &
- status, and a terminal emulator program ( source ) featuring file
- transfer using XMODEM, YMODEM, and YMODEM-G.
-
- Registration for PCL4P is $65 plus $3 S&H ($6 outside of the USA,
- Canada, an Mexico) and includes printed documentation, a library
- without the shareware screen, and SOURCE code for the library.
-
-
-
-
-
-
-
-
-
-
- Users Manual page 22
- 13.0 License
-
- This software and the disks on which it is contained is licensed
- to you, for your own use. This is copyrighted software. You are
- not obtaining title to the software or any copyright rights. You
- may not sublicense, rent, lease, convey, modify, translate, or
- convert this software for any purpose.
-
- You may make as many copies of this software as you need for
- backup purposes. You may use this software on no more than two
- computers at any one time. If you need to use this software on
- more than two computers simultaneously, please contact use for
- information about site licenses.
-
- 14.0 Warranty
-
- MARSHALLSOFT COMPUTING, INC. DISCLAIMS ALL WARRANTIES RELATING TO
- THIS SOFTWARE, WHETHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT
- LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
- FOR A PARTICULAR PURPOSE, AND ALL SUCH WARRANTIES ARE EXPRESSLY
- AND SPECIFICALLY DISCLAIMED. NEITHER MARSHALLSOFT COMPUTING, INC.
- NOR ANYONE ELSE WHO HAS BEEN INVOLVED IN THE CREATION, PRODUCTION,
- OR DELIVERY OF THIS SOFTWARE SHALL BE LIABLE FOR ANY INDIRECT,
- CONSEQUENTIAL, OR INCIDENTAL DAMAGES ARISING OUT OF THE USE OR
- INABILITY TO USE SUCH SOFTWARE EVEN IF MARSHALLSOFT COMPUTING,
- INC. HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR
- CLAIMS. IN NO EVENT SHALL MARSHALLSOFT COMPUTING, INC.'S LIABILITY
- FOR ANY SUCH DAMAGES EVER EXCEED THE PRICE PAID FOR THE LICENSE TO
- USE THE SOFTWARE, REGARDLESS OF THE FORM OF THE CLAIM. THE PERSON
- USING THE SOFTWARE BEARS ALL RISK AS TO THE QUALITY AND
- PERFORMANCE OF THE SOFTWARE.
-
- Some states do not allow the exclusion of the limit of liability
- for consequential or incidental damages, so the above limitation
- may not apply to you.
-
- This agreement shall be governed by the laws of the State of
- Alabama and shall inure to the benefit of Marshallsoft Computing,
- Inc. and any successors, administrators, heirs and assigns. Any
- action or proceeding brought by either party against the other
- arising out of or related to this agreement shall be brought only
- in a STATE or FEDERAL COURT of competent jurisdiction located in
- Madison County, Alabama. The parties hereby consent to in personam
- jurisdiction of said courts.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Users Manual page 23
-